PNPUtil Prepared by Keith Sullivan with help from Scott Kadarally and info from MSDN
Overview
This document proposes a solution to the issue of how to add multiple hardware drivers to the base image for Windows 7. It is recommended that drivers be added via the built-in PNPUtil command line function. Windows 7 introduces a new method of managing drivers by housing them in a database known as a driver store. By using the built-in function PNPUtil, drivers can be added to the image using the task sequencing process. The benefit of using PNPUtil is that is it allows drivers to be added to Windows without the need for creating a software package. This saves time by reducing the number of steps it takes to prepare the drivers for the Windows 7 image. It also removes the need to modify the registry or require any 3rd party applications which could cause problems further down the line. The goal of the process is for users to be able to connect new hardware such as printers to their machine without experiencing any driver location or rights issues thereby reducing calls to the help desk for technical support for help.
Technical Information
A driver file is typically comprised of an .INF file, a .CAT catalogue file, a .SYS file, and a .CAB file. The .INF file provides device and driver information, including the location driver files, registry entries, device IDs, catalogue files, and version information that is required to install the device or driver. The INF is used not only when the device or driver is first installed, but also when the user requests a driver update through Device Manager. When a driver package is copied to the driver store, all of its files are copied including the INF file and all files that are referenced by the INF file. All files that are in the driver package are considered critical to the device installation. The INF file must reference all of the required files for device installation so that they are present in the driver store. If the INF file references a file that is not included in the driver package, the driver package is not copied to the store. After a driver package has passed integrity and syntax checks, it is copied to the driver store located in “C:\Windows\System32\DriverStore”. Afterwards, Windows uses the driver package to automatically install new devices without requiring user interaction.
Prepared by Keith Sullivan with help from Scott Kadarally and info from MSDN
Overview
This document proposes a solution to the issue of how to add multiple hardware drivers to the base image for Windows 7. It is recommended that drivers be added via the built-in PNPUtil command line function.
Windows 7 introduces a new method of managing drivers by housing them in a database known as a driver store. By using the built-in function PNPUtil, drivers can be added to the image using the task sequencing process.
The benefit of using PNPUtil is that is it allows drivers to be added to Windows without the need for creating a software package. This saves time by reducing the number of steps it takes to prepare the drivers for the Windows 7 image. It also removes the need to modify the registry or require any 3rd party applications which could cause problems further down the line.
The goal of the process is for users to be able to connect new hardware such as printers to their machine without experiencing any driver location or rights issues thereby reducing calls to the help desk for technical support for help.
Technical Information
A driver file is typically comprised of an .INF file, a .CAT catalogue file, a .SYS file, and a .CAB file. The .INF file provides device and driver information, including the location driver files, registry entries, device IDs, catalogue files, and version information that is required to install the device or driver. The INF is used not only when the device or driver is first installed, but also when the user requests a driver update through Device Manager.
When a driver package is copied to the driver store, all of its files are copied including the INF file and all files that are referenced by the INF file. All files that are in the driver package are considered critical to the device installation. The INF file must reference all of the required files for device installation so that they are present in the driver store. If the INF file references a file that is not included in the driver package, the driver package is not copied to the store.
After a driver package has passed integrity and syntax checks, it is copied to the driver store located in “C:\Windows\System32\DriverStore”. Afterwards, Windows uses the driver package to automatically install new devices without requiring user interaction.